canon/tiers/99_Tier_99_Operational/T99_Story_Spine_Build_Logic [ACTIVE v3.2].md
Humanity Project — Phase 6 Story Spine Cascade Operational Handbook
Joshua Alexander Milks. CONFIDENTIAL.
Drafted: May 3, 2026\. Replaces T99\_Story\_Spine\_Build\_Logic v2.3 (April 23, 2026 through May 2, 2026 patches). v3.1 PATCH May 17, 2026 — three drift corrections per v5-Operational CI authoring session: §1 Activation Preconditions CI version reference update to v5-Operational, §4.1 T1\_Tier\_B\_DLC\_Catalog removal from always-loaded foundation per DRAFT v0.1 state, §4.2 Tier 0 Drive folder path correction to canonical 00\_Tier\_0\_Master\_Indices. v3.2 PATCH May 17, 2026 — Pre-Chunk-5A Cleanup propagation per CVD v1.4 plus T1\_WGM v2.2 canonical-name locks: Appendix A Ch 66-69 entries reframed to canonical names (Atlantis retained per CVD §3 Component 1 anchor list; Pohljar plus Tiamarath plus Maatherion fresh-original); §6 Step 8 canonical question category reference updated; §7.7 Grid 3 SQ11 Lost Civilizations chapter naming propagated.
Status: ACTIVE through Phase 6 Spine Cascade close. Retires at Final Range Review pre-Prologue 9-grid lock plus Prologue plus Ch 1 build complete plus Final Consolidation Protocol execution. Memory marker at retirement: HUM-STORY-SPINE-COMPLETE.
Drive placement: /Humanity/99\_Tier\_99\_Operational/T99\_Story\_Spine\_Build\_Logic.
This is the operational handbook for Phase 6 Spine Cascade execution. Phase 6 authors per-chapter Spine entries across 79 nodes covering Ch 2 through Ch 77 plus Epilogue plus Prologue plus Ch 1 against the locked Canonical Vision Document foundation and the locked T1\_Build\_Pipeline\_Contracts §9 Story Spine canonical authority. This doc instructs the Phase 6 Spine Cascade agent and the author-in-loop collaborator on session-by-session execution mechanics.
This doc is operational. World canon authority lives at CVD plus the T1 Foundation domain docs plus the T0 canonical registries. Pipeline contract canonical authority lives at T1\_Build\_Pipeline\_Contracts. This doc operates within those authorities and never supersedes them.
This document IS:
This document IS NOT:
Doc lifecycle anchor: this doc is Type B operational protocol per T1\_Architecture\_and\_State Type A/B/C taxonomy. Section anchor IDs are the canonical retrieval-stable references (Section 7.4 Grid Revision Trigger Protocol, Section 11.6 Final Consolidation Protocol, Appendix A Stage 2 Canonical Question Review Reference, etc.). External docs cite this handbook by section anchor.
This doc activates when all of the following are true:
If any precondition is false, session halts and surfaces the failed precondition to author. Phase 6 cascade does not begin on incomplete foundation — the foundation is the substrate.
Why Phase 6 builds on locked CVD and locked §9: Phase 6 cascade authors canonical chapter-level main story spine entries that downstream pipelines (Region Page Build §7, Quest Writing §6, Cinematic §5, AIVA §3, ElevenLabs §4, UE5 §1) consume at chapter substrate. Drift in CVD framing or §9 schema during cascade execution would propagate downstream as cascade-tainted spine entries. CVD plus §9 must be locked before cascade authoring begins.
Why Phase 6 builds before Region Page Build §7 cascade: Per §9.9 cross-pipeline linkages, Region Page Build reads T1\_Story\_Spine per the region's chapter set at Section 13 Quest Framework Main Story Questline authoring. Spine cascade close gates Region Page Build readiness per the region's chapter set; per-region cascade authoring proceeds when all chapters in the region's chapter set reach locked spine\_status per §9.7. Spine establishes protagonist arc; Region Page Build references Spine for arc-level content at Section 12.1 Protagonist Path Through This Region cross-references.
Why Phase 6 builds before Project 4 Quest Writing detail: Per §6.9 cross-pipeline linkages plus this section §11.5, Spine provides the what-and-why of personal arc; Quest Writing provides the how-and-when in detail. Every quest produced in Project 4 must serve a Spine arc beat.
When a Claude session activates this doc, the session declares the session identity block before any execution step proceeds.
\===SESSION IDENTITY===
Session type: Story Spine Build (per-chapter authoring) OR Range Review (per Section 7). Session scope: Build T1\_Story\_Spine entry for Chapter \[N\] OR Range Review Ch \[X\] through Ch \[Y\]. Build order position: \[X of 79 total nodes — Ch 2 through Ch 77 plus Epilogue plus Final Range Review plus Prologue plus Ch 1\] per Section 3 Build Order. Spine\_status target at session close: drafted (per §9.7 seven-state machine for non-hard-line; eight-state machine for canonical hard-line per §9.4.1 Stage 2 canonical\_question\_review insert). Canonical\_hard\_line\_flag: TRUE or FALSE per §9.2 canonical hard-line spine set membership (18 chapters: Prologue, Ch 1, Ch 8, Ch 29, Ch 38, Ch 42, Ch 55, Ch 57, Ch 58, Ch 65, Ch 66, Ch 67, Ch 68, Ch 69, Ch 74, Ch 76, Ch 77, Epilogue). Input docs loaded: per Section 4 Input Docs Per Chapter Session. Output target: per-chapter spine entry append to T1\_Story\_Spine canonical Drive doc plus structured-field scatter to T0 registries per §9.6. Collaboration mode: Spine Cascade agent proposes creatively within canon; author reviews per Decision 4B all-chapters-author-in-loop discipline; canonical hard-line chapters route through Stage 2 canonical\_question\_review per §9.4.1.
\===END SESSION IDENTITY===
Session is not reference mode. Not Restructure mode. Not Region Building mode. Not Quest Writing mode. It is Spine Cascade mode — a dedicated session type with its own execution rules per Section 6 Per-Session Execution Procedure.
Order per Decision 2A sequential cascade ordering: Ch 2 → Ch 3 → Ch 4 → ... → Ch 77 → Epilogue → Final Range Review pre-Prologue 9-grid lock → Prologue → Ch 1\.
Rationale: Ch 2 is the canonical entry point of the 77-chapter adventure arc (Prologue and Ch 1 are origin tutorial). Building the adventure spine first produces a complete personal-arc framework, which then informs how the Prologue and Ch 1 tutorial setup should flow. Building Prologue first risks committing tutorial decisions that conflict with arc requirements discovered later. Per author canonical decision: Prologue plus Ch 1 are the most-canon-dependent chapters in the build — pre-rift familiar selection mechanic, 12-species roster, Origin tutorial — and must build against fully-locked canon. The Final Range Review locks the 9 grids comprehensively across the full Ch 2-77 plus Epilogue range so that Prologue plus Ch 1 build against final-form canon.
Pace: One chapter per session. Per-chapter session is expected to consume roughly 60 to 80 percent of a Claude session's context budget given input loads, substrate research, and output production. Two chapters per session risks context overflow and consistency drift.
Sequential, not parallel: each chapter entry builds on continuity from previous chapters. Protagonist age, companions present, homes established, identity-hiding pressure, integrity divergence state — all these accumulate chapter to chapter. Parallel session production would create discontinuity.
Range Review gating per Decision 5A 9-grid apparatus lock: every 10 chapters (Ch 12, 22, 32, 42, 52, 62, 72\) a dedicated Range Review Session runs per Section 7\. Ch \[N\] Range Review must close before Ch \[N+1\] begins. No forward chapter builds across an open Range Review. Plus one Final Range Review between Epilogue completion and Prologue/Ch 1 build per Section 7.7 (9-grid lock). Eight Range Reviews total across build.
Phase 8 Ch 12 first Range Review note: per Phase 5 plan, Phase 8 follows Phase 7 Project 1 v3.8-Spine custom instructions update. Ch 12 first Range Review audits Ch 2-11 prior cascade work as audit baseline. Ch 2-11 prior work serves as audit baseline against new CVD plus the 9-grid apparatus per §9.7. Good and aligned content preserved and deepened against new CVD; drift content rewritten through Range Review revision-log entries per Section 7.4 Grid Revision Trigger Protocol.
Total session estimate: 77 chapter sessions plus 1 Epilogue plus 2 Prologue/Ch 1 (after Final Range Review locks canon) plus 8 Range Reviews (7 mid-arc plus 1 Final) \= approximately 88 sessions.
Calendar estimate: at one chapter per focused session, approximately 15 to 25 sessions per concentrated weekend at the author's measured pace — Spine builds in 4 to 6 concentrated weekends. Calendar slips do not invalidate the build; one chapter per session, sequential, against locked canon.
Every Spine Cascade session reads the following docs at session start. Some are always-loaded per Project 1 v3.8-Spine custom instructions; some are loaded on-demand via read\_file\_content for Drive gdocs or via T0 sheet access for canonical registries.
Loaded into every Phase 6 Spine Cascade session per Project 1 v3.8-Spine attachment:
Loaded on-demand at field population per §9.6 per-registry spine column adds. Twenty-nine canonical T0 sheets plus T0\_Schema\_Dictionary doc at /Humanity/00\_Tier\_0\_Master\_Indices/ at gdrive folder ID 1ni2qIY44X47qZ26fxPCU7lF2RL6AEJPZ, twenty-one at active populate per T1\_AaS v3.2:
Schema authority lives at T1\_Build\_Pipeline\_Contracts §9.5 (per-chapter Spine entry schema) plus §9.6 (per-registry spine column adds). This section does not duplicate schema canon. Read §9 directly at session start for canonical schema authority. This section owns operational authoring guidance — body prose voice, scope discipline, decision marker discipline, cultural authenticity at body prose layer.
Per-chapter Spine entry minimum-viable schema per §9.5:
Structured fields scatter to existing T0 registries per §9.6 column adds. No new T0 registry creates per Decision 1B body-prose-dominant Spine architecture. Read §9.6 for full per-registry column specification including T0\_Chapter\_Index extensive adds (protagonist\_age, identity\_hiding\_status arrays, vimana\_precursor\_seed, mode\_variety\_check, etc.), T0\_Worldstate\_Variables integrity\_divergence object, T0\_Familiar\_Registry familiar\_bond\_character\_by\_path, T0\_Antagonist\_Network\_Registry hostile\_recognition\_node\_array, and other per-registry additions.
Body prose target: 200-400 words per chapter per §9.5 prose scope.
Voice: close-third personal-arc narration. The protagonist is the lens. The reader is inside the protagonist's perception, not above it. This is not omniscient narration. It is not first-person confessional. The camera sits over the protagonist's shoulder, and the language carries the protagonist's substrate state in every sentence per CVD §15.1.
Anti-duplication rule per §9.5 prose scope: body prose carries arc-level not region-detail content. Region detail belongs in T8 Region Pages per Pipeline §7 region page authoring. Scene detail belongs in T0\_Scene\_Spec\_Registry scene anchors per Pipeline §5 cinematic scene assembly. Dialogue belongs in T0\_Quest\_Definition\_Registry quest dataset per Pipeline §6 quest writing.
In-scope for body prose:
Out-of-scope for body prose:
Example body prose for Ch 8 Swahili Coast at approximately 370 words:
At nine years old, the protagonist arrives at the Swahili Coast — the first time they have crossed open water since leaving Flores. The journey has taught them something about the shape of the world: that distance can hide them better than caves, that strangers across oceans share more vocabulary than expected, that survival is increasingly about navigating people and not just terrain. The old fisherman who teaches them navigation does not ask about their ears, kept hidden under a cloth wrap against the sun.
This chapter is where commerce begins as a canonical practice — not trade as profession but trade as relationship. The protagonist learns that buying and selling is also a kind of language, that what you carry into a market and what you carry out reveals you. Coastal cultures are crossroads, and crossroads are where someone hiding can hide better. The protagonist files this lesson alongside the others: each region teaches a new way to be invisible.
The found-family beat of this chapter is the fisherman himself — a widowed man who takes the protagonist in as an apprentice not because he is paid but because his own grandchild died of fever the previous monsoon. The attachment forms slowly, around shared work and shared silences. By chapter end, the protagonist has a place they could return to. The three paths diverge subtly at the moment of departure: on the good path, they promise to return; on the neutral path, they leave the promise ambiguous; on the bad path, they take what the fisherman has saved and slip away before dawn. Within-path level variation: on Path A, L1 Truly Good leaves something in return; L2 Good just promises return.
\[DECISION NEEDED \- JOSH: Does Trade 10 Fishing/Navigation home base mechanic canonically anchor here as a home the protagonist can return to across the arc, or does the protagonist lose contact with this fisherman after Ch 8?\]
Captures arc without writing scenes. Notice what is not in the prose: no description of dhow architecture, no list of what is sold in Kilwa markets, no documentation of Swahili-Arab-Persian-Indian maritime culture specifics. Those live in T8\_Region\_Swahili\_Coast Sections 1 through 11\. Spine prose stays at protagonist arc level.
Decision marker format: \[DECISION NEEDED \- JOSH: specific question\]. Every decision the Spine Cascade agent cannot make from existing canon without inventing surfaces here for author resolution at Stage 4 author review per §9.4.1.
Target: 3 to 8 decision markers per chapter entry. More than 10 markers indicates session producing too much speculation; fewer than 2 markers indicates session not probing canon deeply enough. Outside this range triggers concern surfaced to author.
When the Spine Cascade agent is uncertain whether to flag or invent, the answer is flag. Per the v4-Restructure CI Decision Discipline principle inherited at v3.8-Spine: better to flag a decision the author thinks trivial than silently invent canon. Invented canon at scale is the drift signature observed in Ch 2-12 prior cascade work and prevented by this discipline.
Canonical hard-line chapters per §9.2 carry additional Stage 2 canonical\_question\_review per §9.4.1 — specific canonical question categories per Appendix A. Stage 2 surfaces canonical questions before Stage 3 baseline authoring begins where canonical substrate is ambiguous, where path-conditional branching surfaces decisions beyond CVD or T1 reference scope, where Cassius Velheim antagonist family identity decisions surface beyond canonical authority, where Grand Sage reveal hard line risk surfaces, where convergence node path commitment requires path-bucket-distinct authoring beyond Five Integrity Three Path canonical specification, where fairy-realm-script arc anchor authoring surfaces decisions about identification timing per CVD §17.9 pre-Ch-8 reveal prohibition, where cultural depiction at high-care chapters surfaces CVD §17.1 hard line decisions.
CVD §6 cultural depiction standard binds at body prose authoring. CVD §17.1 cultural depiction hard lines bind absolute. Cultural authenticity at body prose layer cascades from §8 Book Processing corpus query layer plus T1 reference doc canon plus prior canonical lock state.
High-care cultural set per CVD §6.2: Ch 29 Sámi, Ch 42 Haiti, Ch 57 Australia. These chapters route through canonical\_question\_review at Stage 2 per §9.4.1 plus author-in-loop review at Stage 4 per Decision 4B. Body prose authoring at high-care chapters:
Elevated care cultural set per CVD §6.2: Ch 11 Congo, Ch 12 East African, Ch 13 South Africa, Ch 47-48 Mesoamerica, Ch 50 Amazon. Elevated care chapters route through author-in-loop review at Stage 4 per Decision 4B without additional Stage 2 canonical\_question\_review state but carry batch-level cultural authenticity audit at Range Review.
Per CVD §17.1 universal cultural depiction hard lines binding at all body prose authoring: respectful artistic depiction; primary-source-grounded; never combat against community representatives; never Hollywood film tropes; never stereotyped descriptors (no "tribal," "primitive," "exotic," "world music"); registered and protected cultural property referenced not reproduced (AIATSIS-registered Aboriginal artwork, joiks, protected ceremonial elements).
Eleven-step walkthrough per Phase 6 Spine Cascade session. Aligned with §9.4.1 six-stage author-in-loop workflow. No skipping. No reordering.
Declare session identity block per Section 2\. State which chapter this session is building. Confirm build order position per Section 3\. Confirm canonical\_hard\_line\_flag per §9.2 (TRUE for the 18-chapter canonical hard-line set covering Prologue, Ch 1, Ch 8, Ch 29, Ch 38, Ch 42, Ch 55, Ch 57, Ch 58, Ch 65, Ch 66, Ch 67, Ch 68, Ch 69, Ch 74, Ch 76, Ch 77, Epilogue; FALSE otherwise).
Check all preconditions in Section 1\. Plus session-level gating check: verify the most recent Range Review (if any preceded current chapter range) is CLOSED. If a Range Review is open and current chapter is in the next range, halt and surface to author. No forward chapter builds across an open Range Review per Section 7.1 Range Review Gating.
If any precondition fails, halt and flag to author. Do not proceed on incomplete state.
Load all Section 4.1 always-loaded foundation docs into context, including this doc (T99\_Story\_Spine\_Build\_Logic v3.0) and Section 7.5 Living Revision Log within it. If any doc is missing, flag and halt — author must confirm doc is still canonical and in current ACTIVE state.
Load Section 4.2 Tier 0 registries via direct sheet access at field population time. Read T0\_Chapter\_Index for chapter row plus referenced foreign keys (region\_id, character\_ids, familiar\_ids, weapon\_ids, boss\_ids, thread\_ids). Read other T0 registries on-demand at field population.
Load Section 4.3 docs covering T3\_Core\_Characters, T3\_Supporting\_Characters, T3\_Familiars\_Named, T4\_House\_of\_Velheim\_Canonical.
Read previous chapter's Spine entry from T1\_Story\_Spine canonical Drive doc via read\_file\_content. Extract continuity inputs:
Then read Section 7.5 Living Revision Log accumulated entries. Extract any revision entries that affect the current chapter's structured-field scatter — thread reroutes, ability bucket renames, familiar class reassignments, weapon category moves, recognition-mechanism subtype additions per any in-cascade canonical surface. Apply latest naming and alignment when populating §9.6 structured-field scatter at Step 9\.
This is continuity anchoring plus revision-log alignment. Drift prevention starts here.
If this is Ch 2 (first chapter built sequential), there is no previous Spine entry. Use Ch 1 canonical framework as the start state — protagonist at canonical age, pre-rift familiar bonded per Ch 1 character creation surface, healer's child best-friend gender per Ch 1 selection, rift fall placing protagonist in Flores cave at Ch 1 end. Flag explicitly: "Ch 2 start state derived from Ch 1 canonical framework (Ch 1 Spine entry built later after Ch 2-77 plus Epilogue plus Final Range Review complete)."
Stage 1 of §9.4.1 author-in-loop workflow: substrate read.
Execute §8 Book Processing corpus query layer call scoped to chapter. Filter via chapter\_scope\_hints set to chapter\_id plus region\_tags set to chapter region context plus optional content\_filter set to relevant content type (cultural anthropology, comparative mythology, regional history, etc.). Retrieve corpus chunks with citations.
Compose goal anchoring preamble before producing any Spine entry content:
\===GOAL ANCHORS===
Chapter: CH\_\[NN\] Region: \[region\_primary from T0\_Chapter\_Index\] Era: \[era from T0\_Chapter\_Index\] Threads served: \[array from T1\_Threads\_22 intersecting this chapter per T0\_Thread\_Grid lookup\] Cultural-depiction tier: \[maximum / elevated / standard per CVD §6.2\] CVD §17 hard lines applicable: \[subset relevant to this chapter\] Pillars applicable: \[1.1 through 1.13 subset; especially Pillar 1.12 Mode Variety and Pillar 1.13 Three-Layer Engagement\] 11-Component Thesis components surfacing: \[subset per CVD §3 anchored in this chapter\] Living Revision Log entries applicable: \[any §7.5 entries affecting this chapter's grids\] Canonical hard-line flag: \[TRUE/FALSE per §9.2\] Stage 2 canonical question categories: \[if hard-line, per Appendix A; else NONE\] Previous chapter end state: \[brief summary from Step 6\] Next chapter start requirements: \[brief summary from T0\_Chapter\_Index next\_chapter row\] §8 corpus query results: \[brief summary of retrieved chunks plus citations\]
\===END GOAL ANCHORS===
Every field of the Spine entry produced below must trace to at least one anchor. Unanchored content equals drift, flagged at Stage 4 author review.
Stage 2 of §9.4.1 author-in-loop workflow: canonical question review (canonical hard-line set only per §9.2).
If canonical\_hard\_line\_flag is FALSE, skip to Step 9\.
If canonical\_hard\_line\_flag is TRUE, surface canonical questions per Appendix A category set for this chapter. Categories cover:
Author resolves canonical questions before authoring proceeds. Resolutions feed back into canonical store at T1 doc patches, T0 registry row updates, or CVD §19 Restructure Log entries. Resolutions are durable canon, not session-scoped — subsequent chapters reading the same canonical substrate read the resolved state.
If author defers a canonical question, document the deferral and proceed to Stage 3 with explicit deferred-decision flag in §9.6 structured-field scatter for that field.
Stage 3 of §9.4.1 author-in-loop workflow: baseline authoring compose and execute.
Compose structured authoring prompt per chapter including chapter identity frame, canonical chapter structure substrate per T0\_Chapter\_Index plus T1 references, retrieved §8 corpus chunks with citations, T1 reference doc context per §9.3 dependency mapping, T0 registry lookup context per §9.6 column adds, T3 plus T4 character substrate, prior chapter spine entry continuity input from Step 6, hard line discipline per CVD §17 plus per-chapter canonical\_hard\_line\_flag, integrity-and-path framework per T1\_Integrity\_Paths\_Worldstates\_Master Five Integrity Three Path framework, body prose target 200-400 words per §9.5 prose scope, structured-field scatter target per §9.6 column adds, Stage 2 canonical question resolutions if hard-line.
Submit composed prompt to Spine Cascade LLM per build pipeline configuration. LLM model selection pins per chapter category at build pipeline configuration alongside UE5 engine version, Meshy agent version, AIVA agent version, ElevenLabs model version, Quest Writer LLM model version, Cinematic Director agent version, Region Builder LLM model version per §9.4 access pattern.
LLM returns baseline chapter content covering body prose plus structured-field T0 registry foreign-key population substrate.
Mid-scope checkpoint per Section 9.2 anti-drift protocol: at approximately 200 words of body prose, halt and self-check:
Resume or revise based on checkpoint.
Stages 4 and 5 of §9.4.1 author-in-loop workflow: author review and refinement-or-rejection.
The author-in-loop step routes baseline chapter content into author review at T1\_Story\_Spine doc plus T0 registry sheet surface. Author evaluates baseline against:
Author signs off OR refines OR rejects.
If author signs off at first pass, chapter spine\_status flips to drafted per §9.7 state machine. Proceed to Step 11\.
If refinement is needed, author adjusts via authoring iteration covering body prose tuning, structured-field scatter correction, T0 registry foreign-key population adjustment, integrity-divergence per-path framing refinement, anti-duplication scope correction. Iteration may surface canonical questions that escalate back to Stage 2 canonical question review for hard-line chapters; resolutions feed back into canonical store before re-authoring proceeds.
If author rejects, the agent regenerates with refined authoring intent parameters. Regeneration counts against iteration budget per chapter.
Iteration budget per chapter: target one to three iterations to convergence. Budget exceeded surfaces escalation to canonical-substrate-gap diagnosis per §9.4.1 human-in-loop escalation triggers (canonical substrate ambiguous and requires CVD or T1 reference clarification, CVD §17 hard line risk surfaces during refinement, cultural authenticity audit flags chapter for review, canonical substrate gap requires CVD or T1 doc patch before chapter authoring can proceed).
Stage 6 of §9.4.1 author-in-loop workflow: final chapter spine entry lock.
Author-signed-off chapter content locks chapter spine entry to T1\_Story\_Spine canonical Drive doc plus T0 registry foreign-key population to canonical T0 sheets. last\_authored\_timestamp updates to current ISO-8601. spine\_status flips to drafted per §9.7 state machine — drafted awaits Range Review at next 10-chapter window for transition through range\_reviewed and ratified states to locked.
Author-in-loop session log captures intent revisions, authoring refinement notes, canonical question resolutions if hard-line, and convergence count for chapter retrospective. Session log does not write to canonical store; lives in build session logs adjacent to the Spine Cascade agent operational store.
At session end, produce two handoffs per Project 1 v3.8-Spine custom instructions handoff discipline. Finalized Spine entries delivered as canonical paste-ready content for T1\_Story\_Spine Drive doc append.
Handoff 1 — next message in this session (if author responds with corrections):
Author reviews Ch \[N\] Spine entry produced this session. Author provides resolutions to \[DECISION NEEDED \- JOSH\] markers (Spine Cascade agent updates entry inline), corrections to any field or prose beat, approval to finalize entry. Agent updates entry with corrections, produces final version, author copies to T1\_Story\_Spine Drive doc plus structured-field scatter to T0 registries.
Handoff 2 — new session for Ch \[N+1\]:
Per Phase 6 Spine Cascade new-session prompt template. Includes: load this doc T99\_Story\_Spine\_Build\_Logic v3.0 plus Section 7.5 Living Revision Log accumulated entries; load all Section 4.1 always-loaded foundation docs; load chapter-specific Section 4.4 docs for Ch \[N+1\]; load Section 4.3 character and antagonist reference; load continuity anchor previous chapter Spine entry plus Section 7.5 Living Revision Log; verify activation preconditions per Section 1 plus Range Review gating; execute eleven-step procedure for Ch \[N+1\].
Memory marker convention: per-chapter Spine markers deprecated. Canonical completion record equals T1\_Story\_Spine Drive doc append plus T0 registry foreign-key population. File memory markers only for HUM-SPINE-RANGE-REVIEW-Ch-NN-COMPLETE (8 total at Ch 12, 22, 32, 42, 52, 62, 72, plus FINAL) plus HUM-STORY-SPINE-COMPLETE (final). Nine markers total across full Spine build.
After every 10 chapters built (Ch 12, 22, 32, 42, 52, 62, 72), a dedicated Range Review Session runs. Plus one Final Range Review between Epilogue completion and Prologue/Ch 1 build per Section 7.7. Range Review is not a chapter build — it is audit plus revision-log only.
9-grid roster authority lives at T1\_Build\_Pipeline\_Contracts §9.7. This section owns operational mechanics: gating discipline, output format, grid revision trigger protocol, Living Revision Log mechanics, Range Review does not produce spine entries rule, Final Range Review pre-Prologue 9-grid lock.
Range Reviews are gating checkpoints, not advisory audits. The Ch \[N\] Range Review must close before any chapter in the next range begins.
Closure conditions (all required):
If closure conditions are not all met, the Range Review remains open. No Ch \[N+1\] forward build. Halt-and-flag to author.
Why gating: drift in canonical grids compounds silently across chapters if not audited at meaningful intervals. Catching drift at Ch 22 is far cheaper than catching it at Ch 72\. Cascade-era observations through Ch 11 build (recognition-mechanism subtype canonical surfacing, structural-antagonist-limit dual-anchor canonical pattern, trade community-substrate schema canonical surfacing, reputation-biography propagation system canonical existence) demonstrate that canonical content emerges across chapters and Range Review is the structural mechanism that captures cumulative emergence without per-session ad-hoc canonical doc updates.
Per §9.7 9-grid Range Review apparatus locked at Decision 5A. Each Range Review session audits the just-completed 10-chapter range against 9 canonical grids:
Read §9.7 directly for per-grid audit specification. This handbook does not duplicate per-grid roster canon.
Each grid checks bucket-assignment integrity, distribution health, and progression coherence against the relevant canonical doc. Drift remediation flows through Section 7.4 Grid Revision Trigger Protocol producing revision-log entries to Section 7.5 Living Revision Log.
Range Review Report filed to T1\_Story\_Spine canonical Drive doc as a dedicated section. Format per range:
Section header: Range Review Ch \[start chapter through end chapter\]
Per-grid report block (one per 9 grids):
Cross-grid pattern findings (one block):
Closure block (one):
When a grid audit surfaces drift, file a revision-log entry to Section 7.5 Living Revision Log. Entry format:
\[Range Review Ch NN-MM\] Grid: \[grid name\]. Drift: \[description of drift detected\]. Resolution: \[proposed canonical resolution or pending author decision\]. Reason: \[why this resolution preserves canonical integrity\].
Mid-build revision-log entries also permitted: if a principle or drift or clarification surfaces during a chapter session, the agent files a mid-build entry to Section 7.5 with timestamp. Range Reviews serve as confirmation checkpoints for accumulated entries against the just-completed range.
What NOT to do at Range Review:
All canonical doc updates and retroactive Spine entry alignment happen at Final Consolidation per Section 11.6, applied as a single batched event. Living Revision Log accumulates the deltas; consolidation applies them in batch.
This subsection accumulates revision-log entries across all Range Reviews (Ch 12, 22, 32, 42, 52, 62, 72\) plus Final Range Review per Section 7.7. Append-only during Phase 6 Spine Cascade. Read by all subsequent chapter range builds as canonical revision context. Archived at HUM-STORY-SPINE-COMPLETE per Section 11.6 Final Consolidation Protocol.
How subsequent chapter sessions use this log: Step 6 of every chapter session reads the Living Revision Log. Any revision entry affecting the current chapter's grids gets applied to §9.6 structured-field scatter during Step 9 Stage 3 baseline authoring (e.g., if Range Review Ch 12 added a sub-bucket under Thread 17, then Ch 23's relevant content uses that sub-bucket directly).
How Final Consolidation uses this log: Section 11.6 reads the entire accumulated log, applies all deltas to canonical docs in batch through dedicated canonical doc patch sessions, retroactively aligns earlier Spine entries Ch 2-77 plus Epilogue plus Prologue plus Ch 1 to final naming, and archives this section as \[ARCHIVED Living Revision Log\] in /\_Archive\_Story\_Spine\_Build\_Logic/.
Migration note for v2.3 entries: Living Revision Log Entries 1-21 from v2.3 do not carry forward to v3.0. Entries 1-17 cascade-era findings absorbed into canonical T1 plus T0 docs through Phase 5 Restructure work. Entries 18-21 are canonical content findings that migrate to canonical T1 plus T0 plus T3 plus T4 docs per Appendix B Phase 5M Migration Queue. v3.0 Living Revision Log starts empty at Phase 6 launch.
Log entries (append below this line — empty at v3.0 lock):
\--- LIVING REVISION LOG \---
\[Entries populate during Phase 6 Spine Cascade at per-session and per-Range-Review intervals\]
\--- END LIVING REVISION LOG \---
Range Review is audit plus revision-log only. Any Spine entry revisions happen at Final Consolidation per Section 11.6 as a batched retroactive alignment, OR if author directly requests immediate revision of a specific entry. Range Review itself does not produce or rewrite chapter Spine entries.
The reason: rewriting Spine entries during Range Review creates session-context conflict with chapter-cascade authoring. Range Review focuses on audit. Consolidation happens at Final Consolidation as a single coherent retroactive pass reflecting full-arc learning.
Exception: if a grid audit surfaces a hard-line violation (CVD §17 violation) in a previously-completed chapter Spine entry, the violation triggers an immediate revision session for that specific entry. Hard-line violations are not deferred. Memory marker for revision: HUM-SPINE-REVISION-Ch-NN-COMPLETE.
Trigger: Epilogue Spine entry filed and approved. Ch 73-77 plus Epilogue not yet Range-Reviewed (last regular Range Review was at Ch 72).
Purpose: Final 9-grid lock across the full Ch 2-77 plus Epilogue arc before Prologue plus Ch 1 build. The Final Range Review is gating — Prologue/Ch 1 builds cannot begin until this review closes.
Why this checkpoint exists per author canonical decision: Prologue plus Ch 1 are the most-canon-dependent chapters in the build. They contain pre-rift familiar selection mechanic at Ch 1 pre-rift (player interacts with all 12 elven-realm species), 12-species roster lock (must match what the rest of the arc references), Origin tutorial canon (must align with everything established Ch 2-77 plus Epilogue), family plus Architect chronology (5,000-year framework per CVD §17.12 plus T4 canonical), rift fall mechanics plus Ch 2 cave awakening setup, all systems and identities the rest of the arc has been building backward references to.
These chapters cannot build against drifting or unlocked canon. The Final Range Review locks the 9 grids comprehensively across the full arc so that Prologue plus Ch 1 build against final-form canon.
Scope: same 9 grids per §9.7, applied across the full Ch 2-77 plus Epilogue range:
Closure conditions (all required):
If closure conditions are not all met, no Prologue/Ch 1 build. Halt-and-flag to author.
Spine Cascade is collaborative. The Spine Cascade agent and the author share authoring responsibilities per §9.4 access pattern Decision 4B all-chapters-author-in-loop discipline plus §9.4.1 six-stage author-in-loop workflow.
Per chapter:
Per canonical hard-line chapter (additional):
Per Range Review (every 10 chapters plus Final Range Review pre-Prologue):
No chapter is canonical until author approves at Stage 6\. Agent-produced Spine entries are drafted state until author-approved, then drafted progresses through the §9.7 state machine to range\_reviewed (at Range Review), ratified (at Range Review handoff plus cross-chapter coherence verified), and locked (canonical lock state for downstream pipelines).
Agent creativity permitted:
Agent creativity NOT permitted without author approval:
When in doubt: flag as \[DECISION NEEDED \- JOSH\] rather than invent. Better to flag a decision the author thinks trivial than silently invent canon.
Phase 6 cascade across 88 sessions risks drift. These protocols are foundational discipline.
Per Section 6 Step 7\. Every session's content must trace to declared anchors in the goal anchoring preamble, including Living Revision Log entries applicable to current chapter. Unanchored content equals drift, flagged at Stage 4 author review.
Per Section 6 Step 9\. At approximately 200 words of body prose, halt and self-check against in-scope and out-of-scope discipline plus Pillar 1.13 three-layer engagement plus T8 anti-duplication. Errors cluster mid-generation; mid-scope checkpoint catches them before they propagate to chapter-end output.
Per Section 6 Step 6\. Previous chapter's end state equals current chapter's start state. Hard constraint. Drift here cascades across the entire remaining arc. Plus Living Revision Log alignment at Step 6 read.
Every 10 chapters plus Final Range Review pre-Prologue, 9-grid audit catches drift the per-chapter protocols missed. Range Review GATING per Section 7.1 — no forward chapter builds across an open Range Review.
Target 3 to 8 \[DECISION NEEDED \- JOSH\] markers per chapter entry per Section 5.4. Outside this range triggers concern:
The agent does not revisit previously-completed Spine entries unless:
Otherwise, prior entries are canonical — forward-build from them, do not rewrite them.
Every chapter must serve all three layers per Pillar 1.13 three-layer engagement architecture:
If any layer is underdeveloped, flag and revise before finalizing per §9.7 Stage 4 author review.
Every chapter where integrity-path divergence pivots must address all three paths in the integrity\_divergence object plus path\_state\_at\_chapter\_end per §9.6 column adds. Paths are not optional — Truly Good, Good Enough, Evil all receive distinctive feedback at chapter level. Within-path level variation per T1\_Integrity\_Paths\_Worldstates\_Master Five Integrity Three Path framework noted optionally where L1/L2/L3/L4/L5 has distinctive feedback in this chapter beyond path-bucket framing.
Per CVD §7.2 three paths produce three distinct Finale endings; intermediate bands produce textural variation within the closest path's Finale, not distinct endings. Spine cascade authors all three paths at chapter pivot points. Three-ending differentiation at Ch 77 plus Epilogue is hard line per Section 5.5 cultural authenticity discipline plus §9.8 cultural authenticity discipline.
Per Section 6 Step 6\. Read accumulated Living Revision Log entries at session start. Apply latest naming and alignment when populating §9.6 structured-field scatter at Step 9\. Mid-build revision-log entries permitted per Section 7.4 — file at session close if a principle, drift, or clarification surfaces during a chapter session.
Per cascade-era observation across Ch 2-12 prior cascade work, certain pitfalls recur. Section 10 names them and the prevention discipline.
Symptom: body prose drifts into describing specific scenes, dialogue, camera shots, choreographed combat sequences.
Prevention: Section 5.2 in-scope and out-of-scope discipline plus Section 6 Step 9 mid-scope checkpoint.
Rule: body prose carries arc-level not scene-detailed content. Scene detail belongs in T0\_Scene\_Spec\_Registry per Pipeline §5 Cinematic. Dialogue belongs in T0\_Quest\_Definition\_Registry per Pipeline §6 Quest Writing.
Symptom: chapters start reading the same. Same emotional tone, same identity-hiding tension level, same found-family beat structure.
Prevention: Section 6 Step 6 continuity anchor plus Section 7 Range Review Grid 1 (Thread Grid distribution health) plus Pillar 1.12 Mode Variety plus per-chapter Pillar 1.10 Regional Combat Identity.
Rule: each chapter has a distinct mountain-range peak per CVD §16.1 mountain-range principle. Each chapter has a distinct mode-variety profile per CVD §16.2 mode variety per chapter.
Symptom: things happen TO the protagonist; the protagonist does not choose, decide, act in pivotal moments.
Prevention: Section 5.2 voice discipline (close-third personal-arc narration; protagonist is the lens, not above the events) plus integrity\_divergence per §9.6 column adds (divergence\_points\_this\_chapter array per chapter forces three-path active choices).
Rule: every chapter has at least one pivotal protagonist choice that nudges integrity per Five Integrity Three Path framework. Per CVD §7.1 paths are accumulated through play, not selected — the chapter must surface accumulated patterns through actual protagonist choices.
Symptom: body prose drifts into didactic lecturing about cultural specifics, ritual mechanics, religious frameworks.
Prevention: Section 5.2 anti-duplication rule (region detail belongs in T8 Region Pages) plus Section 5.5 cultural authenticity at body prose layer (substrate-respectful upstream framing without compositing didactic exposition).
Rule: body prose references cultural texture; T8 Region Pages document cultural detail; §8 Book Processing corpus carries primary-source substrate. Each layer has its own scope.
Symptom: chapters proceed without addressing identity-hiding tension or recognition events.
Prevention: identity\_hiding\_status\_start array plus identity\_hiding\_status\_end array plus identity\_hiding\_pressure per §9.6 column adds populated for every chapter. Cumulative recognition-state canon per identity\_hiding\_status array — multiple recognition types simultaneously active surface as multi-element array values.
Rule: identity-hiding pressure is a continuous arc thread, not a per-chapter optional. Chapters where pressure is LOW still surface the LOW state explicitly. Recognition events at canonical chapters (Ch 6 Vedda, Ch 7 Guruji, Ch 8 Sayyid hostile-recognition first instance plus Ch 8 Mwalimu Hassan plus Mijikenda kaya elder positive-recognition, Ch 9 Ge'ez, Ch 11 Mbuti land-recognition, Ch 17 Architect first contact, Ch 23 Eleusinian, Ch 28 Roman administrative, Ch 46 Cold-War, Ch 58 Antarctica, Ch 69 the Duat, Ch 76 Cassius Velheim) surface in identity\_hiding\_status array plus found\_family\_state.hostile\_recognition\_node\_array per §9.6.
Symptom: chapters proceed without addressing home-building or home-state context.
Prevention: homes\_state object per §9.6 column adds populated for every chapter — homes\_established\_prior, home\_established\_this\_chapter, home\_lost\_this\_chapter, home\_activity\_this\_chapter.
Rule: home-building is canonical mechanic. Homes accumulate; homes can be lost; homes can be revisited. Per CVD §7.4 Truly Good path texture includes "world responds with respect and openness" and home-building is one operational expression.
Symptom: attachments form and dissolve without weight; named NPCs feel interchangeable.
Prevention: found\_family\_state per §9.6 column adds with attachment\_tier\_changes\_array tracking per-NPC tier shifts (incidental, acquainted, known, close, bonded) plus prior\_attachments\_active carrying forward.
Rule: found-family attachments persist across chapters and accumulate weight through repeat encounters. Healer's child best-friend per Ch 1 selection is the highest-priority relationship ledger per CVD §9.4.
Symptom: Path A, Path B, Path C divergence at chapter pivots reads as cosmetic — same outcome with different framing.
Prevention: integrity\_divergence.divergence\_points\_this\_chapter array per §9.6 column adds requires path\_a\_action\_good, path\_b\_action\_neutral, path\_c\_action\_bad as canonically distinct actions. Per Pillar 9 Decision 8 audit at Range Review Grid 6 Convergence Node verifies divergence points are genuine, not equivalent re-skinnings.
Rule: paths are operationally distinct, not cosmetically distinct. Per CVD §7 three paths produce three distinct Finale endings; per-chapter pivot moments must contribute to that distinction with actions that genuinely differ.
Symptom: agent proposes major arc beats, NPC backstories, plot-altering decisions without canon backing.
Prevention: Section 8.4 Creative Latitude Boundaries plus Section 5.4 Decision Marker Discipline plus Section 9.5 Protocol 5\.
Rule: when the agent is uncertain whether to flag or invent, flag. Invented canon at scale is the drift signature observed in cascade-era prior work and prevented by this discipline. Per CVD §17.14 plus inheritance from v4-Restructure CI: better to flag a decision the author thinks trivial than silently invent canon.
Symptom: agent generates extensive content for fields where canon is sparse.
Prevention: Section 5.4 decision marker discipline target 3-8 markers; Section 6 Step 7 goal anchoring (every field must trace to anchor); Section 9.5 Protocol 5 marker discipline.
Rule: sparse canon yields short content plus markers, not extensive speculation. The agent extracts from canon, then flags gaps. The agent does not fill gaps creatively in canonical authoring scope.
Symptom: chapter structured fields drift from canonical bucket naming over the cascade — Trade naming uses old labels, ability tree nodes use deprecated names, familiar class assignments use cascade-era labels.
Prevention: Section 6 Step 6 Living Revision Log alignment at session start. Read accumulated revision entries; apply latest naming.
Rule: bucket naming is canonical at the state of last revision-log entry plus locked T1 reference. Drift from canonical naming surfaces at Range Review Grid audits per Section 7.2 plus §9.7 9-grid roster.
Symptom: cultural-context awareness applied as hard prohibition or gating mechanism beyond canonical scope ("the protagonist can never X because culture Y reveres it"; "respect 5 cultures' sacred animals to unlock legendary").
Prevention: Section 5.5 cultural authenticity at body prose layer plus CVD §6 cultural depiction standard plus CVD §17.1 cultural depiction hard lines.
Rule: local cultural consequence in local cultural context. No global propagation. No gating beyond canon. Sacred-status species can still be bonded familiars per canonical 22-slot architecture. Pillar 1.13 governs: the game is a fun action-adventure RPG first.
Spine is complete when:
This is the critical handoff: once locked, T1\_Story\_Spine canonical Drive doc becomes one of the always-loaded canonical docs for every downstream Project session per T1\_Architecture\_and\_State Per-Project File Loading section. Spine is not just consumed once — it is attached to every Project 2 through Project 7 session as foundational context per the per-project file load specifications.
Always-attached usage by Project per cross-pipeline linkages at §9.9:
Once locked, Spine is canonical. Downstream projects operate within Spine constraints, do not overwrite them. If any downstream project identifies a Spine correction needed, that triggers a Spine Revision session, not a downstream silent override.
Spine Revision session: single chapter Spine entry rebuilt with corrections through the Section 6 Per-Session Execution Procedure. New entry replaces old in T1\_Story\_Spine canonical Drive doc plus T0 registry foreign-key population updated. Memory marker: HUM-SPINE-REVISION-Ch-NN-COMPLETE. Revision is rare; significant scope drift implies methodology problem and warrants halt-and-discuss with author.
Substrate-driven re-authoring cascade per §9.7 regeneration\_required state: canonical chapter row content change since last\_authored\_timestamp, referenced T1 doc content change, referenced T0 registry row change impacting chapter scope, T3 character canon update, T4 antagonist family canon update, §8 Book Processing corpus expansion, schema migration affecting authoring intent structure all flip spine\_status to regeneration\_required and trigger targeted re-authoring per Spine Revision session protocol.
Section 11.4 Handoff to v4 Restructure Blueprint retired. Restructure Blueprint v4.1 ARCHIVED at Session 5L Distribution close per T1\_Architecture\_and\_State Authority Hierarchy. Spine handoff to Restructure scope no longer applicable; Restructure already executed before Phase 6 cascade begins.
Pipeline §6 Quest Writing is where Spine has the deepest downstream impact. Quest writing for any chapter loads:
The quest writer produces:
Spine provides the what-and-why; Pipeline §6 provides the how-and-when in detail.
At HUM-STORY-SPINE-COMPLETE, a final consolidation event runs as the closing event of Phase 6 Spine Cascade. Final Consolidation operates at Spine-side scope; canonical T1 doc updates required by accumulated Living Revision Log deltas execute through dedicated canonical doc patch sessions adjacent to Final Consolidation, not within it.
Trigger: author declares Spine complete (final chapter built, Final Range Review pre-Prologue 9-grid lock closed, Prologue plus Ch 1 built, Epilogue built). Memory marker HUM-STORY-SPINE-COMPLETE filed.
Scope (Spine-side):
Why batched (Spine side): distributing Spine-entry retroactive alignment across 79 chapter sessions creates noise and conflict risk. Batching at Spine completion ensures Spine entries receive one coherent retroactive pass reflecting full-arc learning.
Why canonical doc updates execute outside Final Consolidation: T1 plus T0 plus T3 plus T4 canonical doc updates require their own dedicated patch sessions per Authority Hierarchy plus per-doc canonical lock state. Final Consolidation surfaces the deltas; canonical patch sessions apply them. The two are sequential, not coincident.
Before launching Phase 6 Spine Cascade Ch 2 first session, verify:
If all checklist items pass, Phase 6 cascade launches at Ch 2 first session per Section 6 Per-Session Execution Procedure.
Per §9.4.1 Stage 2 canonical\_question\_review state for the 18-chapter canonical hard-line set per §9.2. Each hard-line chapter surfaces canonical question categories before Stage 3 baseline authoring begins. Author resolves canonical questions; resolutions feed back into canonical store at T1 doc patches, T0 registry row updates, or CVD §19 Restructure Log entries.
This appendix names what each hard-line chapter surfaces. Specific canonical questions per chapter session emerge during Stage 2 read of canonical substrate plus §8 corpus query layer plus prior chapter spine entry.
Per v3.0 Living Revision Log handling decision: v3.0 ships with empty Section 7.5 Living Revision Log. Phase 6 cascade builds the log fresh. Entries 18-21 from v2.3 are canonical content findings that migrate to canonical T1 plus T0 plus T3 plus T4 docs, NOT carried in v3.0 operational handbook.
Migration targets per entry:
Source: v2.3 §7.5 Living Revision Log Entry 18 (April 27, 2026, Ch 11 Congo / Ituri Forest trigger).
Canonical content: recognition-via-individual-perceiver subtypes (empty-space register, embodied-practice register, tendi-tradition register, kaya-elder-protocol register, liturgical-individual-perceiver register, family-network register) plus recognition-via-land first-instance (Ch 11 Mbuti hunter — "the forest already knows").
Migration target: T3\_Core\_Characters or T1\_Integrity\_Paths\_Worldstates\_Master at recognition-mechanism subtype canonical schema.
Phase 5 session: 5K (T3 Core, T3 Supporting refines plus T0\_Character\_Index populate) OR 5F (T1\_Integrity\_Paths\_Worldstates refine plus T0\_Worldstate\_Variables populate).
Ch 02-11 retro-applicability per Entry 18: pattern emerged as canonical at Ch 11; prior chapters retain their original recognition-mechanism canonical registrations via the entry's category schema. No prior-chapter Spine entry rewrites required per Section 9.6 forward-build canon.
Forward-arc generative pattern: future region builds either map to existing recognition-mechanism subtype (selecting one) or register a new subtype (Range Review Grid 6 Convergence Node audit criterion) per §9.7. Subtypes are not strictly mutually exclusive — a region can layer mechanisms — but the dominant register canonically registers per chapter.
Source: v2.3 §7.5 Living Revision Log Entry 19 (April 27, 2026, Ch 11 Congo / Ituri Forest trigger).
Canonical content: knowledge embodied in bodies and relationships rather than in texts and institutions is structurally uncapturable by an antagonist-network apparatus designed to capture texts and institutions. Two canonical anchors register the pattern: Ch 7 Tamil Siddha (institutional shutdown but knowledge persists in lineage-substrate) and Ch 11 Ituri Forest (Sayyid surveillance baseline operationally fails at pre-civilizational territorial depth where knowledge lives in body-and-relationship-substrate rather than institutional surface).
Migration target: T4\_House\_of\_Velheim\_Canonical §8 antagonist-network operational topology canon at Phase 5K (T4 Velheim refines plus T0\_Antagonist\_Network\_Registry populate).
Forward-arc structural-antagonist-limit anchor regions per Entry 19: Ch 13 Drakensberg San (distributed pre-civilizational tradition), Ch 22 nomadic-steppe (mobile community-substrate), Ch 49 Amazon uncontacted (FUNAI distance plus territorial depth), Ch 57 Australia (Aboriginal songline-substrate), Ch 58 Antarctica (no human-civilizational surface), Ch 69 the Duat (canonical hidden-civilization). These regions canonically register Velheim-intrusion permitted scope as STRUCTURALLY FAILS where applicable.
T4 §8 antagonist-network operational topology audit at Ch 12 Range Review Grid 6 Convergence Node review per §9.7: verify Sayyid network operational-reach failure documented; verify forward-arc structural-antagonist-limit anchor regions registered; confirm structural-condition-not-personal-escape canonical framing.
Source: v2.3 §7.5 Living Revision Log Entry 20 (April 27, 2026, Ch 11 Congo / Ituri Forest trigger).
Canonical content: Trade-master schema canonical refinement introducing community-substrate schema as structurally distinct second register alongside institutional-individual schema. Trade-master canonical schema covers institutional-individual (named master, location, lineage) plus community-substrate (community as Trade-master, place-as-master, lineage-as-distributed-substrate).
Migration target: T1\_Trades\_Master at Phase 5I (T1\_Trades\_Master populate).
T1\_Trades\_Master integration: schema distinction surfaces at trade-master canonical framing across all 10 trades. Some trades have institutional-individual home-base structure (e.g., Trade 5 Alchemy Persia institutional-individual); some have community-substrate structure (e.g., Trade 1 Animal Communication Mbuti net-hunting protocol community-substrate). Both legitimate, structurally distinct.
Range Review Grid 2 Trade Questline audit criterion per §9.7 verifies trade-master schema applied per canonical structure per trade.
Source: v2.3 §7.5 Living Revision Log Entry 21 (April 27, 2026, Ch 11 Congo / Ituri Forest trigger).
Canonical content: reputation-biography propagation system canonical existence — schema field writes per chapter action carry path-and-integrity-variant fields across applicable entity types (quests plus NPCs plus regions/markers); concealment-mode-aware writes scoped per applicable network (CONCEALMENT\_WITH\_RECOGNIZED\_ALLY scoped to ally network, CONCEALMENT\_WITH\_HOSTILE\_RECOGNITION scoped to antagonist-network intelligence record private register, OPEN\_PRESENCE scoped to public record per era plus location); marker-entry function establishing canonical existence and core distinctions for future chapter Spine entries.
Migration target: T0\_Worldstate\_Variables existence registration at Phase 5F (T1\_Integrity\_Paths\_Worldstates refine plus T0\_Worldstate\_Variables populate). Plus post-cascade architecture gap full spec at T1\_Personal\_Dimension\_Spec adjacent.
T0\_Worldstate\_Variables registration: reputation-biography propagation system schema field substrate registers at canonical existence level. Full system spec deferred to post-cascade architecture gaps queue (alongside personal dimension system spec, Solo DLC pre-identification catalog, MMO regional biography variation system per existing canonical post-cascade gap inventory). Full spec produced post-summer book processing per Project 2 sequence canon.
Cross-references per Entry 21: v2.2 §5.1 identity\_hiding\_status array canon (concealment-mode interaction); T4\_House\_of\_Velheim\_Canonical antagonist-network intelligence record canon (CONCEALMENT\_WITH\_HOSTILE\_RECOGNITION write target); MMO regional biography variation system (post-cascade architecture gaps queue — canonical relationship: MMO system operates on the same schema field substrate as solo / DLC propagation; guild integrity in MMO Tier C affects schema field writes; Tier A solo and Tier B DLC use the same schema substrate without guild-integrity overlay); structural-antagonist-limit dual-anchor canon Entry 19 (community-substrate-schema home schema field writes structurally protected from antagonist-network capture).
Phase 5M T0\_Schema\_Dictionary populate work absorbs the four migration items at the appropriate Phase 5 session (5F, 5I, 5K). Each entry's canonical content lands in its target canonical doc as canonical substrate; v3.0 Section 7.5 Living Revision Log starts empty for Phase 6 cascade.
If canonical migration of any entry is incomplete at Phase 6 launch, the entry surfaces at Phase 6 Spine Cascade Stage 2 canonical question review for the chapter where the entry's canonical content first applies (Ch 11 Congo for Entries 18-21 origin chapter, or earlier chapters that retroactively register the canonical content per Range Review Grid 6 Convergence Node audit at Ch 12).
End of T99\_Story\_Spine\_Build\_Logic v3.0.